Determination Of Non-Voice Emergency Service Availability

ABSTRACT

Determining if non-voice emergency services (NOVES) are available is accomplished via an indicator provided via a control channel and/or via a query to a network entity. For example, a NOVES indicator can be provided, via a control channel message, to a communications device, indicating whether non-voice emergency services (NOVES) are available or not available. Additionally, capabilities of public safety answering points (PSAPs) providing NOVES can be included. For example, the indicator can include information as to whether an identified PSAP can receive a text based emergency message, an emergency message comprising an image, and emergency message comprising audio, and/or an emergency message comprising video. In another example configuration, a communications device can query a communications network to determine the availability of NOVES and PSAP capabilities. A response to the query can include an indication as to whether non-voice services are available, and, if appropriate, the types of NOVES services available.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/929,413, filed Jun. 27, 2013, entitled DETERMINATION OF NON-VOICEEMERGENCY SERVICE AVAILABILITY, which is now U.S. Pat. No. 9,002,318,issued Apr. 7, 2015, which is a divisional application of, and claimspriority to, U.S. patent application Ser. No. 13/114,742, filed May 24,2011, which is now U.S. Pat. No. 8,503,975, issued Aug. 6, 2013, all ofwhich are incorporated herein by reference in their entirety.

TECHNICAL FIELD

The technical field generally relates to public safety, and morespecifically relates to determining if non-voice emergency services(NOVES) are available.

BACKGROUND

A non-voice emergency service (NOVES) can provide users thereof theability to send a non-voice emergency message to an emergency servicescenter, such as a 911 call center. However, not all emergency servicecenters are equipped to handle non-voice emergency messages.

SUMMARY

Methods and systems are described herein for determining if non-voiceemergency services (NOVES) are available. In an example embodiment, aNOVES indicator is included in a control channel message provided to acommunications device. The NOVES indicator can indicate if NOVES areavailable or if NOVES are not available. When NOVES are available, theNOVES indicator also can indicate the types of NOVES services available,such as images, video, text, audio, etc. That is, for example, indicatewhether the types of NOVES service include an emergency message caninclude a text based emergency message, an emergency message comprisingan image, an emergency message comprising audio, and/or an emergencymessage comprising video. In another example embodiment, a mobilecommunications device can query a communications network to determinethe availability of NOVES capabilities. A response to the query caninclude an indication as to whether non-voice services are available.The response to the query also could include information pertaining tothe types of NOVES services available, such as images, video, text,audio, etc.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example indication of NOVES being available.

FIG. 2 depicts an example indication of NOVES not being available.

FIG. 3 illustrates an example system and process for determining ifnon-voice emergency services are available.

FIG. 4 is a flow diagram of an example process for determining NOVESavailability via an indicator.

FIG. 5 is a flow diagram of an example process for determining NOVESavailability via a query.

FIG. 6 is a block diagram of an example wireless communications devicethat is configurable to determine if non-voice emergency services areavailable.

FIG. 7 is a block diagram of an example NOVES message server.

FIG. 8 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichdetermining if non-voice emergency services are available can beimplemented.

FIG. 9 illustrates an architecture of a typical GPRS network in whichdetermining if non-voice emergency services are available can beimplemented.

FIG. 10 illustrates an exemplary block diagram view of a GSM/GPRS/IPmultimedia network architecture within which determining if non-voiceemergency services are available can be implemented.

FIG. 11 illustrates a PLMN block diagram view of an exemplaryarchitecture in which determining if non-voice emergency services areavailable may be incorporated.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

As described herein, determining if non-voice emergency services (NOVES)are available or not can be accomplished via various mechanisms. In oneexample embodiment, a NOVES indicator can be provided to acommunications device, indicating whether non-voice emergency services(NOVES) are available or not available. The NOVES indicator can beprovided via an appropriate mechanism to the communications device. Forexample, the NOVES indicator can be sent to a communications device viaa control channel message. The NOVES indicator can comprise a bit orbits indicating whether NOVES are available. The NOVES could beindicative of NOVES availability on a cell site basis. The availabilityof NOVES on a cell site basis can be predefined in coordination with apublic safety answering point (PSAP) that is handling the area coveredby the cell site. If all PSAPs within the coverage area of the cell sitesupport NOVES, the NOVES indicator could be set to indicate that NOVESare available. If none of the PSAPs within the coverage area of the cellsite support NOVES, the NOVES indicator could be set to indicate thatNOVES are not available. For example, the NOVES indicator could becontained on the LTE Broadcast Control Channel (BCCH), the LTE CommonControl Channel (CCCH), or the LTE Dedicated Control Channel (DCCH). Themobile device can monitor these control channels to also receiveinstructions on connection to the LTE radio access network. The NOVESindicator can be maintained in the RAN configuration information withinthe eNodeB.

In an example embodiment, the communications device could interpret theNOVES indicator, and render an indication as to the availability ofNOVES. The indication of availability of NOVES could be rendered in anyappropriate manner. For example, as depicted in FIG. 1, thecommunications device could display an icon 12, or the like, indicatingthat NOVES are available. As depicted in FIG. 2, the communicationsdevice could display an icon 14, or the like, indicating that NOVES arenot available. In various example embodiments, the indication ofavailability of NOVES could be rendered via sound and/or mechanically(e.g., vibration). In another example embodiment, an icon, such as icon12, could indicate that NOVES are available, and the lack of an iconcould indicate that NOVES are not available. When a user of acommunications device attempts to send a non-voice emergency message,the communications device could check the status of the NOVES indicatorbit, and could immediately inform the user of the availability or lackof availability of NOVES capabilities.

In an example configuration, responsive to receipt of the NOVESindicator, the communications device can store the NOVES indicator (inmemory in the communications device for example), or any appropriateindication of NOVES availability obtained from the NOVES indicator. Thestored information pertaining to NOVES availability can be accessed toprovide the rendered indications described above. When the communicationdevice receives another NOVES indicator, the updated NOVES indicator, oran appropriate indication of NOVES availability obtained from theupdated NOVES indicator can be stored in the communications device.

FIG. 3 illustrates an example system and process for determining ifnon-voice emergency services are available. A communications device 16may have an application or the like, installed on the communicationsdevice 16, to determine if NOVES are available. When this NOVESapplication is initiated, the communications device 16 may initiate andsend a query, at steps 28 and 30, to a NOVES server 22 via a wirelessnetwork 18, to determine if NOVES are available. As described herein,the NOVES capabilities are received from the PSAP and this informationis provisioned in the eNodeB. However, for this example configuration,the NOVES information is stored on a PSAP configuration databaseassociated with a NOVES server. This PSAP configuration informationcould identify the PSAP and its associated PSAP boundaries could alsoidentify its NOVES capability. The NOVES Server could utilize the PSAPconfiguration database in conjunction with the Network configurationdatabase to (1) determine which PSAP provides coverage for the mobiledevice's current location and (2) to determine whether or not that PSAPis NOVES capable. In an example configuration, the communications device16 may be capable of supporting a NOVES address via a messaging service,such as instant messaging, or the like. When the communications device16 detects that a NOVES address has been entered, the communicationsdevice 16 could initiate and send a query, at steps 28 and 30, to aNOVES server 22 via a wireless network 18, to determine if NOVES areavailable.

The query can comprise any appropriate information to determine if NOVESare available. For example, the query can comprise informationindicative of a cellular site handling the region in which thecommunications device is located. The query could comprise informationindicative of the location of the communications device 16, such as, forexample, a location determined by the Global Positioning System (GPS),assisted GPS (A-GPS), time difference of arrival calculations,configured constant location (in the case of non-moving devices), or anycombination thereof.

In an example embodiment, if the query contains information pertainingto the cellular site handling the region in which the communicationsdevice 16 is located (e.g., Cell Site ID), the NOVES 22 server can querya network configuration database 20, at step 32, to retrieve coverageinformation about the indicated cell site. At step 34, the networkconfiguration database provides a response to the query. The coverageinformation provided in the query response (at step 34) can include anyappropriate information. Examples of the information returned could bethe location of the associated cell site and/or the estimated coveragearea of that cell site. Estimated cell site coverage area informationcould be used to identify the one or more PSAPs which provide servicewithin the cell site estimated coverage area. Using the retrieved cellsite coverage information (the information contained in the queryresponse), the NOVES server 22 can query a public safety answering point(PSAP) configuration database 24, at step 36, to identify which PSAP'sboundaries are within the coverage area of the cell site. The NOVESserver 22 also, can query the PSAP configuration database 24, at step36, to determine NOVES capabilities of the identified PSAPs. At step 38,the PSAP configuration database 24 can provide a response to the queryreceived at step 36. In various example embodiments, the query responseprovided at step 38 can include identified PSAPs that handle the regionin which the communications device is located, and additionally caninclude NOVES capabilities of each identified PSAP (e.g., video, text,audio, etc.) This information could indicate the codec and formatencoding types for the multimedia formats such as video, graphics,pictures, and audio.

Upon receiving the query response at step 38, the NOVES server 22processes the information contained in the query response (received atstep 38) to determine if a PSAP or PSAPs covering the region in whichthe communications device 16 is located supports NOVES. All PSAPs incoverage area support NOVES. At steps 40 and 42, the NOVES server 22provides, via the radio access network 18, an indication as to whether aPSAP or PSAPs in the coverage area support NOVES. In an exampleembodiment, the indication provided at steps 40 and 42 comprises anindication that no PSAP in the coverage supports NOVES. In anotherexample embodiment, the indication provided at steps 40 and 42 comprisesan indication that every PSAP in the coverage supports NOVES. In anotherexample embodiment, the indication provided at steps 40 and 42 comprisesan indication that no PSAP in the coverage supports NOVES. In anotherexample embodiment, the indication provided at steps 40 and 42 comprisesan indication of the respective capabilities (video, text, audio, etc.)of each PSAP in the coverage that supports NOVES.

If the query provided at steps 28 and 30 comprises a location of thecommunications device 16, in an example embodiment, the NOVES server 22can query the PSAP configuration database 24, at step 44, to identifywhich PSAP's boundaries cover the location of the communications device16. The Network Configuration Database contains information such as thelocation for cell site (e.g., latitude & longitude), the number ofsectors supported, the orientation of these sectors, and the powerlevels of these sectors. The NOVES server 22 also, can query the PSAPconfiguration database 24, at step 44, to determine NOVES capabilitiesof the identified PSAPs. The PSAP configuration database containsinformation such as the physical address of the PSAP, thetelecommunications address of the PSAP (e.g., telephone numbers, IPaddresses), the coverage area of the PSAP (e.g., polygon defined via aset of latitudes & longitudes), and NOVES capabilities including typesand formats of multimedia communications supported. At step 46, the PSAPconfiguration database 24 can provide a response to the query receivedat step 44. In various example embodiments, the query response providedat step 46 can include identified PSAPs that handle the region in whichthe communications device is located, and additionally can include NOVEScapabilities of each identified PSAP (e.g., video, text, audio, etc.)This information could indicate the codec and format encoding types forthe multimedia formats such as video, graphics, pictures, and audio.

Upon receiving the query response at step 46, the NOVES server 22processes the information contained in the query response (received atstep 46) to determine if a PSAP or PSAPs covering the region in whichthe communications device 16 is located supports NOVES. All PSAPs incoverage area support NOVES. At steps 48 and 50, the NOVES server 22provides, via the radio access network 18, an indication as to whether aPSAP or PSAPs in the coverage area support NOVES. In an exampleembodiment, the indication provided at steps 48 and 50 comprises anindication that no PSAP in the coverage supports NOVES. In anotherexample embodiment, the indication provided at steps 48 and 50 comprisesan indication that every PSAP in the coverage supports NOVES. In anotherexample embodiment, the indication provided at steps 48 and 50 comprisesan indication that no PSAP in the coverage supports NOVES. In anotherexample embodiment, the indication provided at steps 48 and 50 comprisesan indication of the respective capabilities (video, text, audio, etc.)of each PSAP in the coverage that supports NOVES.

Upon receipt of the query response at step 42 or 50, the communicationsdevice can take appropriate action. In an example embodiment, if thequery response, received via step 42 or 50, comprises an indication thatno identified PSAP supports NOVES, the communications device 16 canprovide an indication, via a display, audio, and/or mechanicalvibration, for example, that a voice based call should be initiated,provide an indication that no identified PSAP supports NOVES, or acombination thereof. In another example embodiment, if the queryresponse, received via step 42 or 50, comprises an indication that anidentified PSAP, or identified PSAPs, supports NOVES, the communicationsdevice 16, can initiate a non-voice based message. In another exampleembodiment, the query response, received via step 42 or 50, can comprisean indication that an identified PSAP supports NOVES and the types ofNOVES supported. For example, the response could include an indicationas to whether an identified PSAP can receive a text based emergencymessage, an emergency message comprising an image, and emergency messagecomprising audio, an emergency message comprising video, or anycombination thereof. If the query response, received via step 42 or 50,comprises an indication that an identified PSAP supports NOVES and thetypes of NOVES supported, the communications device 16 can provide anindication, via a display, audio, and/or mechanical vibration, forexample, of the types of NOVES supported, can allow a user to select thetype of NOVES to initiate, and can initiate a non-voice call inaccordance with the type selected.

FIG. 4 is a flow diagram of an example process for determining NOVESavailability via an indicator. At step 52, a NOVES indicator isreceived, by a communications device for example. The NOVES indicatorindicates whether NOVES are available or not available. The NOVESindicator can be received via an appropriate mechanism. For example, theNOVES indicator can be sent to a communications device via a controlchannel message. The NOVES indicator can comprise a bit or bitsindicating whether NOVES are available. The NOVES could be indicative ofNOVES availability on a cell site basis. The available of NOVES on acell site basis can be predefined in coordination with a PSAP that ishandling the area covered by the cell site. If all PSAPs within thecoverage area of the cell site support NOVES, the NOVES indicator couldbe set to indicate that NOVES are available. If none of the PSAPs withinthe coverage area of the cell site support NOVES, the NOVES indicatorcould be set to indicate that NOVES are not available. If some of thePSAPs identified as covering the area, support NOVES, the NOVESindicator could include information indicating which identified PSAPssupport NOVES.

An indication of the NOVES indicator is stored at step 54. In an exampleconfiguration, responsive to receipt of the NOVES indicator, thecommunications device can store the NOVES indicator, or any appropriateindication of NOVES availability obtained from the NOVES indicator.Storage can include memory in the communications device, or externalstorage (external to the communications device), for example.

At step 56 it is determined if an indication of NOVES availability is tobe rendered. The stored information pertaining to NOVES availability canbe accessed to provide the rendered indication of NOVES availability. Ifit is determined, at step 56, that the indication of NOVES availabilityis to be rendered, the indication of NOVES v is rendered at step 58. Theindication of the NOVES availability can be rendered in any appropriatemanner, such as, for example, visually, audibly, and/or mechanically(vibration). In an example configuration, if NOVES are available, avisual indication can be rendered, such as, for example, as depicted inFIG. 1. In an example embodiment, if NOVES are not available, a visualindication can be rendered, such as, for example, as depicted in FIG. 2.In an example embodiment, if NOVES are not available, no indication isrendered. Thus, the lack of an indication (icon, beep, vibration, etc.)could indicate that NOVES are not available.

When the communication device receives another NOVES indicator, theupdated NOVES indicator, or an appropriate indication of NOVESavailability obtained from the updated NOVES indicator can be stored inthe communications device and rendered if appropriate.

An indication to initiate a non-voice emergency call is received at step62. Responsive to receiving the indication to initiate the non-voiceemergency call, the stored indication of the NOVES indicate is analyzedat step 64. At step 66 it is determined if NOVES are available. If, atstep 66, it is determined that NOVES are available, the non-voice basedcall is initiated at step 68. If, at step 66, it is determined thatNOVES are not available, an indication is provided, at step 70, theNOVES are not available. Along with the indication of lack of NOVES,provided at step 70, a message or the like, could be providedinstructions to initiate a voice based emergency call.

FIG. 5 is a flow diagram of an example process for determining NOVESavailability via a query. A non-voice based emergency message isinitiated at step 72. The non-voice based emergency message can beinitiated by any appropriate device, such as, for example, acommunications device (e.g., communications device 16). Thecommunications device may initiate and send a query to determine ifNOVES are available. The query is received at step 74. In an exampleconfiguration, the communications device may be capable of supporting aNOVES address via a messaging service, such as instant messaging, or thelike. When the communications device detects that a NOVES address hasbeen entered, the communications device could initiate and send a queryto determine if NOVES are available.

The query can be received by any appropriate entity. For example, thequery could be received by a network entity, such as a NOVES server(e.g., NOVES server 22), or the like. The query can comprise anyappropriate information to determine if NOVES are available. Forexample, the query can comprise information indicative of a cellularsite handling the region in which the communications device thatprovided the query is located. The query could comprise informationindicative of the location of the communications device that providedthe query, such as, for example, a location determined by the GlobalPositioning System (GPS), assisted GPS (A-GPS), time difference ofarrival calculations, configured constant location (in the case ofnon-moving devices), or any combination thereof.

The query is processed at step 76. In an example embodiment, the queryis processed, at least in part, to determine if information contained inthe query pertains to cell site coverage or a location from which thequery was provided. That is, in an example embodiment, the query isprocessed to determine if the query contains information about thecellular site, or sites, that provides coverage to the region from whichthe query was provided, or if the query contains information about thelocation (e.g., GPS coordinates, or the like) from which the query wasprovided. At step 78, it is determined if the query contains informationpertaining to a cellular site, or sites, or a location of from which thequery was provided. If it is determined, at step 78, that the querycontains information (e.g., cell site identifiers, IDs,) pertaining tothe cellular site(s) handling the region in from which the query wasprovided, the region, or regions, covered by the cell sites aredetermined at step 80. In an example embodiment for example, a networkdatabase can be queried. The network database can comprise anyappropriate entity, such as, for example, network configuration database20. The network database can provided a response to the query includinginformation pertaining to the region, or regions, that are covered bythe cell site(s). At step 82, the PSAP, or PSAPs, that are assigned tohandle the region, or regions, covered by the cell site(s) areidentified. Additionally, at step 82, NOVES capabilities of eachidentified PSAP can be determined. In an example embodiment, forexample, a PSAP database is queried. The PSAP database can comprise anyappropriate entity, such as, for example, PSAP configuration database24.

If it is determined, at step 78, that the query contains informationpertaining the location from which the query was provided, the processproceeds to step 82, wherein the PSAP, or PSAPs, that are assigned tohandle the location are identified. Additionally, at step 82, NOVEScapabilities of each identified PSAP can be determined. For example, itcan be determined if an identified PSAP can receive a text basedemergency message, an emergency message comprising an image, andemergency message comprising audio, an emergency message comprisingvideo, or any combination thereof.

A response to the initial query (received at step 74) is provided atstep 84. The response can comprise any appropriate informationpertaining to NOVES availability. In an example embodiment, the responsecomprises an indication that no identified PSAP supports NOVES. Theresponse can comprise an indication that an identified PSAP, oridentified PSAPs, supports NOVES. In another example embodiment, if thequery response comprises an indication that an identified PSAP supportsNOVES and the types of NOVES (image, video, text, audio, etc.) supportedby each PSAP.

At step 86, the device that initiated the non-voice based message (atstep 72) receives the response and takes appropriate action. If, forexample, the response comprises an indication that no identified PSAPsupports NOVES, the device can provide an indication, via a display,audio, and/or mechanical vibration, for example, that a voice based callshould be initiated, provide an indication that no identified PSAPsupports NOVES, or a combination thereof. If the response comprises anindication that an identified PSAP, or identified PSAPs, supports NOVES,the device can initiate a non-voice based message. If the responsecomprises an indication that an identified PSAP supports NOVES and thetypes of NOVES supported, the device can provide an indication, via adisplay, audio, and/or mechanical vibration, for example, of the typesof NOVES supported, can allow a user of the device to select the type ofNOVES to initiate, and can initiate a non-voice call in accordance withthe type selected. For example, if available, the user could select tosend a text based emergency message, an emergency message comprising animage, and emergency message comprising audio, an emergency messagecomprising video, or any appropriate combination thereof.

FIG. 6 is a block diagram of an example wireless communications device14 that is configurable to determine if non-voice emergency services areavailable. The communications device 14 can include any appropriatedevice, mechanism, software, and/or hardware for determining ifnon-voice emergency services are available as described herein. Asdescribed herein, the communications device 14 comprises hardware, or acombination of hardware and software. And, each portion of thecommunications device 14 comprises hardware, or a combination ofhardware and software. In an example configuration, the communicationsdevice 14 comprises a processing portion 92, a memory portion 94, aninput/output portion 96, a user interface (UI) portion 98, and a sensorportion 100 comprising at least one of a video camera portion 102, aforce/wave sensor 104, a microphone 106, a moisture sensor 108, or acombination thereof. The force/wave sensor comprises at least one of amotion detector, an accelerometer, an acoustic sensor, a tilt sensor, apressure sensor, a temperature sensor, or the like. The motion detectoris configured to detect motion occurring outside of the communicationsdevice, for example via disturbance of a standing wave, viaelectromagnetic and/or acoustic energy, or the like. The accelerator iscapable of sensing acceleration, motion, and/or movement of thecommunications device. The acoustic sensor is capable of sensingacoustic energy, such as a noise, voice, etc., for example. The tiltsensor is capable of detecting a tilt of the communications device. Thepressure sensor is capable of sensing pressure against thecommunications device, such as from a shock wave caused by broken glassor the like. The temperature sensor is capable of sensing a measuringtemperature, such as inside of the vehicle, room, building, or the like.The moisture sensor 108 is capable of detecting moisture, such asdetecting if the communications device 14 is submerged in a liquid. Theprocessing portion 92, memory portion 94, input/output portion 96, userinterface (UI) portion 98, video camera portion 102, force/wave sensor104, and microphone 106 are coupled together to allow communicationstherebetween (coupling not shown in FIG. 6). The communications device14 also can comprise a timer (not depicted in FIG. 6).

In various embodiments, the input/output portion 96 comprises a receiverof the communications device 14, a transmitter of the communicationsdevice 14, or a combination thereof. The input/output portion 96 iscapable of receiving and/or providing information pertaining todetermining if non-voice emergency services are available as describedherein. The input/output portion 96 also is capable of communicationswith the local access network 18 and/or the NOVES server 22, asdescribed herein. For example, the input/output portion 96 can include awireless communications (e.g., 2.5G/3G/GPS) SIM card. The input/outputportion 96 is capable of receiving and/or sending text information,video information, audio information, control information, imageinformation, data, or any combination thereof. In an example embodiment,the input/output portion 96 is capable of receiving and/or sendinginformation to determine a location of the communications device 14. Inan example configuration, the input\output portion 96 comprises a GPSreceiver. In an example configuration, the communications device 14 candetermine its own geographical location through any type of locationdetermination system including, for example, the Global PositioningSystem (GPS), assisted GPS (A-GPS), time difference of arrivalcalculations, configured constant location (in the case of non-movingdevices), any combination thereof, or any other appropriate means. Invarious configurations, the input/output portion 96 can receive and/orprovide information via any appropriate means, such as, for example,optical means (e.g., infrared), electromagnetic means (e.g., RF, WI-FI,BLUETOOTH, ZIGBEE, etc.), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or a combination thereof.In an example configuration, the input/output portion comprises a WIFIfinder, a two way GPS chipset or equivalent, or the like.

The processing portion 92 is capable of determining if non-voiceemergency services are available as described herein. For example, theprocessing portion 92 is capable of, in conjunction with any otherportion of the communications device 14, executing an application forfacilitating provision of a non-voice emergency message, analyzing aNOVES indicator, analyzing a stored indication of a NOVES indicator,initiating a non-voice based emergency message, generating a query,analyzing a query response, generating a text message, generating avoice message, processing a received text message, processing a receivedvoice message, retrieving a predetermined message, processing textmessages provided via the user interface portion 98, processing voicemessages provided via the user interface portion 98, processing textmessages received via the input/output portion 96, processing voicemessages received via the input/output portion 96, or the like, or anycombination thereof. The processing portion 92, in conjunction with anyother portion of the communications device 14, can provide the abilityfor users/subscribers to enable, disable, and configure various featuresof an application for determining if non-voice emergency services areavailable, as described herein. For example, a user, subscriber, parent,healthcare provider, law enforcement agent, of the like, can defineconfiguration parameters such as, for example, an emergency contactlist, voice/text/image/video options for an emergency call, thresholdsettings (e.g., timer settings, signature settings, etc.), to beutilized when sending and/or receiving a text/voice message to/from anemergency call taker. The processing portion 92, in conjunction with anyother portion of the communications device 14, enables thecommunications device 14 to covert speech to text when it is configuredto send text messages while facilitating a 911 voice call from anon-voice message. In an example embodiment, the processing portion 92,in conjunction with any other portion of the communications device 14 asneeded, can convert text to speech for rendering via the user interfaceportion 98.

In a basic configuration, the communications device 14 can include atleast one memory portion 94. The memory portion 94 can store anyinformation utilized in conjunction with determining if non-voiceemergency services are available s described herein. For example, thememory portion 94 is capable of storing information pertaining to aNOVES indicator, an indication of a NOVES indicator, an indication(icon, etc.) that NOVES are available, an indication (icon, etc.) thatNOVES are not available, an indication of an identified PSAP, anindication of a PSAP, an indication of a capability of a PSAP, alocation of a communications device, a predetermined text/voice message,a text/voice message, a predetermined audio/text message, an audio/textmessage, subscriber profile information, subscriber identificationinformation, phone numbers, an identification code of the communicationsdevice, video information, audio information, control information,information indicative sensor data (e.g., raw individual sensorinformation, combination of sensor information, processed sensorinformation, etc.), or a combination thereof. Depending upon the exactconfiguration and type of processor, the memory portion 94 can bevolatile (such as some types of RAM), non-volatile (such as ROM, flashmemory, etc.). The communications device 14 can include additionalstorage (e.g., removable storage and/or non-removable storage)including, tape, flash memory, smart cards, CD-ROM, digital versatiledisks (DVD) or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, universalserial bus (USB) compatible memory, or the like. In an exampleconfiguration, the memory portion 94, or a portion of the memory portion92 is hardened such that information stored therein can be recovered ifthe communications device 14 is exposed to extreme heat, extremevibration, extreme moisture, corrosive chemicals or gas, or the like. Inan example configuration, the information stored in the hardened portionof the memory portion 94 is encrypted, or otherwise renderedunintelligible without use of an appropriate cryptographic key,password, biometric (voiceprint, fingerprint, retinal image, facialimage, or the like). Wherein, use of the appropriate cryptographic key,password, biometric will render the information stored in the hardenedportion of the memory portion 94 intelligible.

The communications device 14 also can contain a UI portion 98 allowing auser to communicate with the communications device 14. The UI portion 98is capable of rendering any information utilized in conjunctiondetermining if non-voice emergency services are available as describedherein. For example, the UI portion 98 can provide means for enteringtext, entering a phone number, rendering text, rendering images,rendering multimedia, rendering sound, rendering video, receiving sound,rendering an indication that NOVES are available, rendering anindication that NOVES are not available, or the like, as describedherein. The UI portion 98 can provide the ability to control thecommunications device 14, via, for example, buttons, soft keys, voiceactuated controls, a touch screen, movement of the mobile communicationsdevice 14, visual cues (e.g., moving a hand in front of a camera on themobile communications device 14), or the like. The UI portion 98 canprovide visual information (e.g., via a display), audio information(e.g., via speaker), mechanically (e.g., via a vibrating mechanism), ora combination thereof. In various configurations, the UI portion 98 cancomprise a display, a touch screen, a keyboard, a speaker, or anycombination thereof. The UI portion 98 can comprise means for inputtingbiometric information, such as, for example, fingerprint information,retinal information, voice information, and/or facial characteristicinformation. The UI portion 98 can be utilized to enter an indication ofthe designated destination (e.g., the phone number, IP address, or thelike).

In an example embodiment, the sensor portion 100 of the communicationsdevice 14 comprises the video camera portion 102, the force/wave sensor104, and the microphone 106. The video camera portion 102 comprises acamera (or cameras) and associated equipment capable of capturing stillimages and/or video and to provide the captured still images and/orvideo to other portions of the communications device 14. In an exampleembodiment, the force/wave sensor 104 comprises an accelerometer, a tiltsensor, an acoustic sensor capable of sensing acoustic energy, anoptical sensor (e.g., infrared), or any combination thereof.

FIG. 7 is a block diagram of an example NOVES message server 22. In anexample embodiment, the NOVES server 22 comprises a network entitycomprising hardware, or a combination of hardware and software. And,each portion of the NOVES message server 22 comprises hardware, or acombination of hardware and software. When used in conjunction with anetwork, the functionality needed to facilitate determining if non-voiceemergency services are available can reside in any one or combination ofNOVES servers. The NOVES server 22 depicted in FIG. 7 represents anyappropriate network entity, apparatus, or combination of networkentities or apparatuses, such as a processor, a server, a gateway, etc.,or any combination thereof. It is emphasized that the block diagramdepicted in FIG. 7 is exemplary and not intended to imply a specificimplementation or configuration. Thus, the NOVES server 22 can beimplemented in a single processor or multiple processors (e.g., singleserver or multiple servers, single gateway or multiple gateways, etc.).Multiple network entities can be distributed or centrally located.Multiple network entities can communicate wirelessly, via hard wire, ora combination thereof.

In an example configuration, the NOVES server 22 comprises a processingportion 110, a memory portion 112, and an input/output portion 114. Theprocessing portion 110, memory portion 112, and input/output portion 114are coupled together (coupling not shown in FIG. 7) to allowcommunications therebetween. The input/output portion 114 is capable ofreceiving and/or providing information from/to a device (e.g.,communications device 14) and/or other emergency message serversconfigured to be utilized when determining if non-voice emergencyservices are available. For example, the input/output portion 112 iscapable of, in conjunction with any other portion of the NOVES server 22as needed, receiving a query, providing an indication of NOVESavailability, providing a query, providing a response to a query,receiving a response to a query, providing a message to a PSAP,receiving a message from a PSAP, providing a message (e.g., query) to aPSAP configuration database, receiving a message (e.g., query response)from a PSAP configuration database, providing a message (e.g., query) toa network configuration database, receiving a message (e.g., queryresponse) from a network configuration database, or the like, or anycombination thereof.

The processing portion 110 is capable of performing functions associatedwith the determining if non-voice emergency services are available, asdescribed herein. For example, the processing portion 110 is capable of,in conjunction with any other portion of the NOVES server 22 as needed,processing a query, determining if a message (e.g., query) containsinformation pertaining to a cellular site from which a query wasreceived, determining if a message (e.g., query) contains informationpertaining to a location from which a query was provided, determining aregion covered by a cellular site, identifying a PSAP assigned to handlea region from which a query was provided, identifying a PSAP assigned tohandle a location from which a query was provided, generating a responseto a message (e.g., query), or the like, or any combination thereof.

The memory portion 112 can store any information utilized in conjunctionwith determining if non-voice emergency services are available, asdescribed herein. For example, the memory portion 112 is capable ofstoring information pertaining to a location of a communications device14, a location of a NOVES server 22, a predetermined text message, atext message, a predetermined audio message, an audio message,subscriber profile information, subscriber identification information,phone numbers, an identification code of the communications device,video information, audio information, control information, informationpertaining to a call taker handling a session, information pertaining toa PSAP handling a specific area or location, a cellular site covering aregion from which a query was provided, a location from which a querywas provided, a NOVES indicator, a region covered by a cell site thatreceived a query, a PSAP assigned to handle a region, a PSAP assigned tohandle a location, a query response, or the like, or a combinationthereof. Depending upon the exact configuration and type of NOVES server22, the memory portion 112 can include a computer storage medium, ormedia, that is volatile 116 (such as dynamic RAM), non-volatile 118(such as ROM), or a combination thereof. The NOVES server 22 can includeadditional storage, in the form of computer storage media (e.g.,removable storage 120 and/or non-removable storage 122) including, RAM,ROM, EEPROM, tape, flash memory, smart cards, CD-ROM, digital versatiledisks (DVD) or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, universalserial bus (USB) compatible memory. As described herein, a computerstorage medium is an article of manufacture.

The NOVES server 22 also can contain communications connection(s) 128that allow the NOVES server 22 to communicate with other devices,network entities, or the like. A communications connection(s) cancomprise communication media. Communication media can be used tocommunicate computer readable instructions, data structures, programmodules, or other data. Communication media can include an appropriatetransport mechanism or information delivery media that can be used totransport a modulated data signal such as a carrier wave.

The NOVES server 22 also can include input device(s) 124 such askeyboard, mouse, pen, voice input device, touch input device, an opticalinput device, etc. Output device(s) 126 such as a display, speakers,printer, mechanical vibrators, etc. also can be included.

The communications device (e.g., communications device 14) and thenetwork entity (NOVES server 22) can be part of and/or in communicationwith various wireless communications networks. Some of which aredescribed below.

FIG. 8 depicts an overall block diagram of an exemplary packet-basedmobile cellular network environment, such as a GPRS network, in whichdetermining if non-voice emergency services are available can beimplemented. In the exemplary packet-based mobile cellular networkenvironment shown in FIG. 8, there are a plurality of Base StationSubsystems (“BSS”) 800 (only one is shown), each of which comprises aBase Station Controller (“BSC”) 802 serving a plurality of BaseTransceiver Stations (“BTS”) such as BTSs 804, 806, and 808. BTSs 804,806, 808, etc. are the access points where users of packet-based mobiledevices become connected to the wireless network. In exemplary fashion,the packet traffic originating from user devices is transported via anover-the-air interface to a BTS 808, and from the BTS 808 to the BSC802. Base station subsystems, such as BSS 800, are a part of internalframe relay network 810 that can include Service GPRS Support Nodes(“SGSN”) such as SGSN 812 and 814. Each SGSN is connected to an internalpacket network 820 through which a SGSN 812, 814, etc. can route datapackets to and from a plurality of gateway GPRS support nodes (GGSN)822, 824, 826, etc. As illustrated, SGSN 814 and GGSNs 822, 824, and 826are part of internal packet network 820. Gateway GPRS serving nodes 822,824 and 826 mainly provide an interface to external Internet Protocol(“IP”) networks such as Public Land Mobile Network (“PLMN”) 850,corporate intranets 840, or Fixed-End System (“FES”) or the publicInternet 830. As illustrated, subscriber corporate network 840 may beconnected to GGSN 824 via firewall 832; and PLMN 850 is connected toGGSN 824 via boarder gateway router 834. The Remote AuthenticationDial-In User Service (“RADIUS”) server 842 may be used for callerauthentication when a user of a mobile cellular device calls corporatenetwork 840.

Generally, there can be a several cell sizes in a GSM network, referredto as macro, micro, pico, femto and umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro-cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 9 illustrates an architecture of a typical GPRS network in whichdetermining if non-voice emergency services are available can beimplemented. The architecture depicted in FIG. 9 is segmented into fourgroups: users 950, radio access network 960, core network 970, andinterconnect network 980. Users 950 comprise a plurality of end users.Note, device 912 is referred to as a mobile subscriber in thedescription of network shown in FIG. 9. In an example embodiment, thedevice depicted as mobile subscriber 912 comprises a communicationsdevice (e.g., wireless anti-theft security communications device 14).Radio access network 960 comprises a plurality of base stationsubsystems such as BSSs 962, which include BTSs 964 and BSCs 966. Corenetwork 970 comprises a host of various network elements. As illustratedin FIG. 9, core network 970 may comprise Mobile Switching Center (“MSC”)971, Service Control Point (“SCP”) 972, gateway MSC 973, SGSN 976, HomeLocation Register (“HLR”) 974, Authentication Center (“AuC”) 975, DomainName Server (“DNS”) 977, and GGSN 978. Interconnect network 980 alsocomprises a host of various networks and other network elements. Asillustrated in FIG. 9, interconnect network 980 comprises PublicSwitched Telephone Network (“PSTN”) 982, Fixed-End System (“FES”) orInternet 984, firewall 988, and Corporate Network 989.

A mobile switching center can be connected to a large number of basestation controllers. At MSC 971, for instance, depending on the type oftraffic, the traffic may be separated in that voice may be sent toPublic Switched Telephone Network (“PSTN”) 982 through Gateway MSC(“GMSC”) 973, and/or data may be sent to SGSN 976, which then sends thedata traffic to GGSN 978 for further forwarding.

When MSC 971 receives call traffic, for example, from BSC 966, it sendsa query to a database hosted by SCP 972. The SCP 972 processes therequest and issues a response to MSC 971 so that it may continue callprocessing as appropriate.

The HLR 974 is a centralized database for users to register to the GPRSnetwork. HLR 974 stores static information about the subscribers such asthe International Mobile Subscriber Identity (“IMSI”), subscribedservices, and a key for authenticating the subscriber. HLR 974 alsostores dynamic subscriber information such as the current location ofthe mobile subscriber. Associated with HLR 974 is AuC 975. AuC 975 is adatabase that contains the algorithms for authenticating subscribers andincludes the associated keys for encryption to safeguard the user inputfor authentication.

In the following, depending on context, the term “mobile subscriber”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 9, whenmobile subscriber 912 initiates the attach process by turning on thenetwork capabilities of the mobile device, an attach request is sent bymobile subscriber 912 to SGSN 976. The SGSN 976 queries another SGSN, towhich mobile subscriber 912 was attached before, for the identity ofmobile subscriber 912. Upon receiving the identity of mobile subscriber912 from the other SGSN, SGSN 976 requests more information from mobilesubscriber 912. This information is used to authenticate mobilesubscriber 912 to SGSN 976 by HLR 974. Once verified, SGSN 976 sends alocation update to HLR 974 indicating the change of location to a newSGSN, in this case SGSN 976. HLR 974 notifies the old SGSN, to whichmobile subscriber 912 was attached before, to cancel the locationprocess for mobile subscriber 912. HLR 974 then notifies SGSN 976 thatthe location update has been performed. At this time, SGSN 976 sends anAttach Accept message to mobile subscriber 912, which in turn sends anAttach Complete message to SGSN 976.

After attaching itself with the network, mobile subscriber 912 then goesthrough the authentication process. In the authentication process, SGSN976 sends the authentication information to HLR 974, which sendsinformation back to SGSN 976 based on the user profile that was part ofthe user's initial setup. The SGSN 976 then sends a request forauthentication and ciphering to mobile subscriber 912. The mobilesubscriber 912 uses an algorithm to send the user identification (ID)and password to SGSN 976. The SGSN 976 uses the same algorithm andcompares the result. If a match occurs, SGSN 976 authenticates mobilesubscriber 912.

Next, the mobile subscriber 912 establishes a user session with thedestination network, corporate network 989, by going through a PacketData Protocol (“PDP”) activation process. Briefly, in the process,mobile subscriber 912 requests access to the Access Point Name (“APN”),for example, UPS.com, and SGSN 976 receives the activation request frommobile subscriber 912. SGSN 976 then initiates a Domain Name Service(“DNS”) query to learn which GGSN node has access to the UPS.com APN.The DNS query is sent to the DNS server within the core network 970,such as DNS 977, which is provisioned to map to one or more GGSN nodesin the core network 970. Based on the APN, the mapped GGSN 978 canaccess the requested corporate network 989. The SGSN 976 then sends toGGSN 978 a Create Packet Data Protocol (“PDP”) Context Request messagethat contains necessary information. The GGSN 978 sends a Create PDPContext Response message to SGSN 976, which then sends an Activate PDPContext Accept message to mobile subscriber 912.

Once activated, data packets of the call made by mobile subscriber 912can then go through radio access network 960, core network 970, andinterconnect network 980, in a particular fixed-end system or Internet984 and firewall 988, to reach corporate network 989.

FIG. 10 illustrates an exemplary block diagram view of a GSM/GPRS/IPmultimedia network architecture within which determining if non-voiceemergency services are available can be implemented. As illustrated, thearchitecture of FIG. 10 includes a GSM core network 1001, a GPRS network1030 and an IP multimedia network 1038. The GSM core network 1001includes a Mobile Station (MS) 1002, at least one Base TransceiverStation (BTS) 1004 and a Base Station Controller (BSC) 1006. The MS 1002is physical equipment or Mobile Equipment (ME), such as a mobile phoneor a laptop computer that is used by mobile subscribers, with aSubscriber identity Module (SIM) or a Universal Integrated Circuit Card(UICC). The SIM or UICC includes an International Mobile SubscriberIdentity (IMSI), which is a unique identifier of a subscriber. The BTS1004 is physical equipment, such as a radio tower, that enables a radiointerface to communicate with the MS. Each BTS may serve more than oneMS. The BSC 1006 manages radio resources, including the BTS. The BSC maybe connected to several BTSs. The BSC and BTS components, incombination, are generally referred to as a base station (BSS) or radioaccess network (RAN) 1003.

The GSM core network 1001 also includes a Mobile Switching Center (MSC)1008, a Gateway Mobile Switching Center (GMSC) 1010, a Home LocationRegister (HLR) 1012, Visitor Location Register (VLR) 1014, anAuthentication Center (AuC) 1018, and an Equipment Identity Register(EIR) 1016. The MSC 1008 performs a switching function for the network.The MSC also performs other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC1010 provides a gateway between the GSM network and other networks, suchas an Integrated Services Digital Network (ISDN) or Public SwitchedTelephone Networks (PSTNs) 1020. Thus, the GMSC 1010 providesinterworking functionality with external networks.

The HLR 1012 is a database that contains administrative informationregarding each subscriber registered in a corresponding GSM network. TheHLR 1012 also contains the current location of each MS. The VLR 1014 isa database that contains selected administrative information from theHLR 1012. The VLR contains information necessary for call control andprovision of subscribed services for each MS currently located in ageographical area controlled by the VLR. The HLR 1012 and the VLR 1014,together with the MSC 1008, provide the call routing and roamingcapabilities of GSM. The AuC 1016 provides the parameters needed forauthentication and encryption functions. Such parameters allowverification of a subscriber's identity. The EIR 1018 storessecurity-sensitive information about the mobile equipment.

A Short Message Service Center (SMSC) 1009 allows one-to-one ShortMessage Service (SMS) messages to be sent to/from the MS 1002. A PushProxy Gateway (PPG) 1011 is used to “push” (i.e., send without asynchronous request) content to the MS 1002. The PPG 1011 acts as aproxy between wired and wireless networks to facilitate pushing of datato the MS 1002. A Short Message Peer to Peer (SMPP) protocol router 1013is provided to convert SMS-based SMPP messages to cell broadcastmessages. SMPP is a protocol for exchanging SMS messages between SMSpeer entities such as short message service centers. The SMPP protocolis often used to allow third parties, e.g., content suppliers such asnews organizations, to submit bulk messages.

To gain access to GSM services, such as speech, data, and short messageservice (SMS), the MS first registers with the network to indicate itscurrent location by performing a location update and IMSI attachprocedure. The MS 1002 sends a location update including its currentlocation information to the MSC/VLR, via the BTS 1004 and the BSC 1006.The location information is then sent to the MS's HLR. The HLR isupdated with the location information received from the MSC/VLR. Thelocation update also is performed when the MS moves to a new locationarea. Typically, the location update is periodically performed to updatethe database as location updating events occur.

The GPRS network 1030 is logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 1032, a cell broadcast and a GatewayGPRS support node (GGSN) 1034. The SGSN 1032 is at the same hierarchicallevel as the MSC 1008 in the GSM network. The SGSN controls theconnection between the GPRS network and the MS 1002. The SGSN also keepstrack of individual MS's locations and security functions and accesscontrols.

A Cell Broadcast Center (CBC) 1017 communicates cell broadcast messagesthat are typically delivered to multiple users in a specified area. CellBroadcast is one-to-many geographically focused service. It enablesmessages to be communicated to multiple mobile phone customers who arelocated within a given part of its network coverage area at the time themessage is broadcast.

The GGSN 1034 provides a gateway between the GPRS network and a publicpacket network (PDN) or other IP networks 1036. That is, the GGSNprovides interworking functionality with external networks, and sets upa logical link to the MS through the SGSN. When packet-switched dataleaves the GPRS network, it is transferred to an external TCP-IP network1036, such as an X.25 network or the Internet. In order to access GPRSservices, the MS first attaches itself to the GPRS network by performingan attach procedure. The MS then activates a packet data protocol (PDP)context, thus activating a packet communication session between the MS,the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services can be used inparallel. The MS can operate in one of three classes: class A, class B,and class C. A class A MS can attach to the network for both GPRSservices and GSM services simultaneously. A class A MS also supportssimultaneous operation of GPRS services and GSM services. For example,class A mobiles can receive GSM voice/data/SMS calls and GPRS data callsat the same time.

A class B MS can attach to the network for both GPRS services and GSMservices simultaneously. However, a class B MS does not supportsimultaneous operation of the GPRS services and GSM services. That is, aclass B MS can only use one of the two services at a given time.

A class C MS can attach for only one of the GPRS services and GSMservices at a time. Simultaneous attachment and operation of GPRSservices and GSM services is not possible with a class C MS.

A GPRS network 1030 can be designed to operate in three networkoperation modes (NOM1, NOM2 and NOM3). A network operation mode of aGPRS network is indicated by a parameter in system information messagestransmitted within a cell. The system information messages dictates a MSwhere to listen for paging messages and how to signal towards thenetwork. The network operation mode represents the capabilities of theGPRS network. In a NOM1 network, a MS can receive pages from a circuitswitched domain (voice call) when engaged in a data call. The MS cansuspend the data call or take both simultaneously, depending on theability of the MS. In a NOM2 network, a MS may not receive pages from acircuit switched domain when engaged in a data call, since the MS isreceiving data and is not listening to a paging channel. In a NOM3network, a MS can monitor pages for a circuit switched network whilereceived data and vice versa.

The IP multimedia network 1038 was introduced with 3GPP Release 10, andincludes an IP multimedia subsystem (IMS) 1040 to provide richmultimedia services to end users. A representative set of the networkentities within the IMS 1040 are a call/session control function (CSCF),a media gateway control function (MGCF) 1046, a media gateway (MGW)1048, and a master subscriber database, called a home subscriber server(HSS) 1050. The HSS 1050 may be common to the GSM network 1001, the GPRSnetwork 1030 as well as the IP multimedia network 1038.

The IP multimedia system 1040 is built around the call/session controlfunction, of which there are three types: an interrogating CSCF (I-CSCF)1043, a proxy CSCF (P-CSCF) 1042, and a serving CSCF (S-CSCF) 1044. TheP-CSCF 1042 is the MS's first point of contact with the IMS 1040. TheP-CSCF 1042 forwards session initiation protocol (SIP) messages receivedfrom the MS to an SIP server in a home network (and vice versa) of theMS. The P-CSCF 1042 may also modify an outgoing request according to aset of rules defined by the network operator (for example, addressanalysis and potential modification).

The I-CSCF 1043, forms an entrance to a home network and hides the innertopology of the home network from other networks and providesflexibility for selecting an S-CSCF. The I-CSCF 1043 may contact asubscriber location function (SLF) 1045 to determine which HSS 1050 touse for the particular subscriber, if multiple HSS's 1050 are present.The S-CSCF 1044 performs the session control services for the MS 1002.This includes routing originating sessions to external networks androuting terminating sessions to visited networks. The S-CSCF 1044 alsodecides whether an application server (AS) 1052 is required to receiveinformation on an incoming SIP session request to ensure appropriateservice handling. This decision is based on information received fromthe HSS 1050 (or other sources, such as an application server 1052). TheAS 1052 also communicates to a location server 1056 (e.g., a GatewayMobile Location Center (GMLC)) that provides a position (e.g.,latitude/longitude coordinates) of the MS 1002.

The HSS 1050 contains a subscriber profile and keeps track of which corenetwork node is currently handling the subscriber. It also supportssubscriber authentication and authorization functions (AAA). In networkswith more than one HSS 1050, a subscriber location function providesinformation on the HSS 1050 that contains the profile of a givensubscriber.

The MGCF 1046 provides interworking functionality between SIP sessioncontrol signaling from the IMS 1040 and ISUP/BICC call control signalingfrom the external GSTN networks (not shown). It also controls the mediagateway (MGW) 1048 that provides user-plane interworking functionality(e.g., converting between AMR- and PCM-coded voice). The MGW 1048 alsocommunicates with other IP multimedia networks 1054.

Push to Talk over Cellular (PoC) capable mobile phones register with thewireless network when the phones are in a predefined area (e.g., jobsite, etc.). When the mobile phones leave the area, they register withthe network in their new location as being outside the predefined area.This registration, however, does not indicate the actual physicallocation of the mobile phones outside the pre-defined area.

FIG. 11 illustrates a PLMN block diagram view of an exemplaryarchitecture in which determining if non-voice emergency services areavailable may be incorporated. Mobile Station (MS) 1101 is the physicalequipment used by the PLMN subscriber. In one illustrative embodiment,communications device 40 may serve as Mobile Station 1101. MobileStation 1101 may be one of, but not limited to, a cellular telephone, acellular telephone in combination with another electronic device or anyother wireless mobile communication device.

Mobile Station 1101 may communicate wirelessly with Base Station System(BSS) 1110. BSS 1110 contains a Base Station Controller (BSC) 1111 and aBase Transceiver Station (BTS) 1112. BSS 1110 may include a single BSC1111/BTS 1112 pair (Base Station) or a system of BSC/BTS pairs which arepart of a larger network. BSS 1110 is responsible for communicating withMobile Station 1101 and may support one or more cells. BSS 1110 isresponsible for handling cellular traffic and signaling between MobileStation 1101 and Core Network 1140. Typically, BSS 1110 performsfunctions that include, but are not limited to, digital conversion ofspeech channels, allocation of channels to mobile devices, paging, andtransmission/reception of cellular signals.

Additionally, Mobile Station 1101 may communicate wirelessly with RadioNetwork System (RNS) 1120. RNS 1120 contains a Radio Network Controller(RNC) 1121 and one or more Node(s) B 1122. RNS 1120 may support one ormore cells. RNS 1120 may also include one or more RNC 1121/Node B 1122pairs or alternatively a single RNC 1121 may manage multiple Nodes B1122. RNS 1120 is responsible for communicating with Mobile Station 1101in its geographically defined area. RNC 1121 is responsible forcontrolling the Node(s) B 1122 that are connected to it and is a controlelement in a UMTS radio access network. RNC 1121 performs functions suchas, but not limited to, load control, packet scheduling, handovercontrol, security functions, as well as controlling Mobile Station1101's access to the Core Network (CN) 1140.

The evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 1130 is aradio access network that provides wireless data communications forMobile Station 1101 and User Equipment 1102. E-UTRAN 1130 provideshigher data rates than traditional UMTS. It is part of the Long TermEvolution (LTE) upgrade for mobile networks and later releases meet therequirements of the International Mobile Telecommunications (IMT)Advanced and are commonly known as a 4G networks. E-UTRAN 1130 mayinclude of series of logical network components such as E-UTRAN Node B(eNB) 1131 and E-UTRAN Node B (eNB) 1132. E-UTRAN 1130 may contain oneor more eNBs. User Equipment 1102 may be any user device capable ofconnecting to E-UTRAN 1130 including, but not limited to, a personalcomputer, laptop, mobile device, wireless router, or other devicecapable of wireless connectivity to E-UTRAN 1130. The improvedperformance of the E-UTRAN 1130 relative to a typical UMTS networkallows for increased bandwidth, spectral efficiency, and functionalityincluding, but not limited to, voice, high-speed applications, largedata transfer and IPTV, while still allowing for full mobility.

An exemplary embodiment of a mobile data and communication service thatmay be implemented in the PLMN architecture described in FIG. 11 is theEnhanced Data rates for GSM Evolution (EDGE). EDGE is an enhancement forGPRS networks that implements an improved signal modulation scheme knownas 11-PSK (Phase Shift Keying). By increasing network utilization, EDGEmay achieve up to three times faster data rates as compared to a typicalGPRS network. EDGE may be implemented on any GSM network capable ofhosting a GPRS network, making it an ideal upgrade over GPRS since itmay provide increased functionality of existing network resources.Evolved EDGE networks are becoming standardized in later releases of theradio telecommunication standards, which provide for even greaterefficiency and peak data rates of up to 1 Mbit/s, while still allowingimplementation on existing GPRS-capable network infrastructure.

Typically Mobile Station 1101 may communicate with any or all of BSS1110, RNS 1120, or E-UTRAN 1130. In a illustrative system, each of BSS1110, RNS 1120, and E-UTRAN 1130 may provide Mobile Station 1101 withaccess to Core Network 1140. The Core Network 1140 may include of aseries of devices that route data and communications between end users.Core Network 1140 may provide network service functions to users in theCircuit Switched (CS) domain, the Packet Switched (PS) domain or both.The CS domain refers to connections in which dedicated network resourcesare allocated at the time of connection establishment and then releasedwhen the connection is terminated. The PS domain refers tocommunications and data transfers that make use of autonomous groupingsof bits called packets. Each packet may be routed, manipulated,processed or handled independently of all other packets in the PS domainand does not require dedicated network resources.

The Circuit Switched—Media Gateway Function (CS-MGW) 1141 is part ofCore Network 1140, and interacts with Visitor Location Register (VLR)and Mobile-Services Switching Center (MSC) Server 1160 and Gateway MSCServer 1161 in order to facilitate Core Network 1140 resource control inthe CS domain. Functions of CS-MGW 1141 include, but are not limited to,media conversion, bearer control, payload processing and other mobilenetwork processing such as handover or anchoring. CS-MGW 1140 mayreceive connections to Mobile Station 1101 through BSS 1110, RNS 1120 orboth.

Serving GPRS Support Node (SGSN) 1142 stores subscriber data regardingMobile Station 1101 in order to facilitate network functionality. SGSN1142 may store subscription information such as, but not limited to, theInternational Mobile Subscriber Identity (IMSI), temporary identities,or Packet Data Protocol (PDP) addresses. SGSN 1142 may also storelocation information such as, but not limited to, the Gateway GPRSSupport Node (GGSN) 1144 address for each GGSN where an active PDPexists. GGSN 1144 may implement a location register function to storesubscriber data it receives from SGSN 1142 such as subscription orlocation information.

Serving Gateway (S-GW) 1143 is an interface which provides connectivitybetween E-UTRAN 1130 and Core Network 1140. Functions of S-GW 1143include, but are not limited to, packet routing, packet forwarding,transport level packet processing, event reporting to Policy andCharging Rules Function (PCRF) 1150, and mobility anchoring forinter-network mobility. PCRF 1150 uses information gathered from S-GW1143, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources and other networkadministration functions. Packet Data Network Gateway (PDN-GW) 1145 mayprovide user-to-services connectivity functionality including, but notlimited to, network-wide mobility anchoring, bearer session anchoringand control, and IP address allocation for PS domain connections.

Home Subscriber Server (HSS) 1163 is a database for user information,and stores subscription data regarding Mobile Station 1101 or UserEquipment 1102 for handling calls or data sessions. Networks may containone HSS 1163 or more if additional resources are required. Exemplarydata stored by HSS 1163 include, but is not limited to, useridentification, numbering and addressing information, securityinformation, or location information. HSS 1163 may also provide call orsession establishment procedures in both the PS and CS domains.

The VLR/MSC Server 1160 provides user location functionality. WhenMobile Station 1101 enters a new network location, it begins aregistration procedure. A MSC Server for that location transfers thelocation information to the VLR for the area. A VLR and MSC Server maybe located in the same computing environment, as is shown by VLR/MSCServer 1160, or alternatively may be located in separate computingenvironments. A VLR may contain, but is not limited to, user informationsuch as the IMSI, the Temporary Mobile Station Identity (TMSI), theLocal Mobile Station Identity (LMSI), the last known location of themobile station, or the SGSN where the mobile station was previouslyregistered. The MSC server may contain information such as, but notlimited to, procedures for Mobile Station 1101 registration orprocedures for handover of Mobile Station 1101 to a different section ofthe Core Network 1140. GMSC Server 1161 may serve as a connection toalternate GMSC Servers for other mobile stations in larger networks.

Equipment Identity Register (EIR) 1162 is a logical element which maystore the International Mobile Equipment Identities (IMEI) for MobileStation 1101. In a typical embodiment, user equipment may be classifiedas either “white listed” or “black listed” depending on its status inthe network. In one embodiment, if Mobile Station 1101 is stolen and putto use by an unauthorized user, it may be registered as “black listed”in EIR 1162, preventing its use on the network. Mobility ManagementEntity (MME) 1164 is a control node which may track Mobile Station 1101or User Equipment 1102 if the devices are idle. Additional functionalitymay include the ability of MME 1164 to contact an idle Mobile Station1101 or User Equipment 1102 if retransmission of a previous session isrequired.

While example embodiments of determining if non-voice emergency servicesare available have been described in connection with various computingdevices/processors, the underlying concepts can be applied to anycomputing device, processor, or system capable of determining ifnon-voice emergency services are available as described herein. Themethods and apparatuses for determining if non-voice emergency servicesare available, or certain aspects or portions thereof, can take the formof program code (i.e., instructions) embodied in tangible storage mediahaving a physical structure, such as floppy diskettes, CD-ROMs, harddrives, or any other machine-readable storage medium having a physicaltangible structure (computer-readable storage medium), wherein, when theprogram code is loaded into and executed by a machine, such as acomputer, the machine becomes an apparatus for determining if non-voiceemergency services are available. A computer-readable storage medium, asdescribed herein is an article of manufacture, and thus, not to beconstrued as a transitory signal. In the case of program code executionon programmable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile and non-volatile memory and/or storage elements), at least oneinput device, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language, and combined with hardwareimplementations.

The methods and apparatuses for determining if non-voice emergencyservices are available can be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,wherein, when the program code is received and loaded into and executedby a machine, such as an EPROM, a gate array, a programmable logicdevice (PLD), a client computer, or the like, the machine becomes anapparatus for determining if non-voice emergency services are available.When implemented on a general-purpose processor, the program codecombines with the processor to provide a unique apparatus that operatesto invoke the functionality of determining if non-voice emergencyservices are available.

While determining if non-voice emergency services are available has beendescribed in connection with the various embodiments of the variousfigures, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for determining if non-voice emergency services areavailable. For example, one skilled in the art will recognize thatdetermining if non-voice emergency services are available as describedin the present application may apply to any environment, whether wiredor wireless, and may be applied to any number of devices connected via acommunications network and interacting across the network. Therefore,determining if non-voice emergency services are available should not belimited to any single embodiment, but rather should be construed inbreadth and scope in accordance with the appended claims.

1. An apparatus comprising: a processor; and memory coupled to theprocessor, the memory comprising at least one executable instructionthat when executed by the processor causes the processor to effectuateoperations comprising: receiving an indication as to whether non-voiceemergency services are available; analyzing the received indication todetermine if non-voice emergency services are available; and when it isdetermined that non-voice emergency services are available, initiating anon-voice emergency message; and when it is determined that non-voiceemergency services are not available, providing an indication non-voiceemergency services are not available.
 2. The apparatus of claim 1,wherein the indication is received via a control channel.
 3. Theapparatus of claim 1, the operations further comprising: providing anindication that non-voice emergency services are available.
 4. Theapparatus of claim 1, the operations further comprising: providing atleast one of: a visual indication that non-voice emergency services areavailable; an audible indication that non-voice emergency services areavailable; or a mechanical indication that non-voice emergency servicesare available.
 5. The apparatus of claim 1, the operations furthercomprising: providing at least one of: a visual indication thatnon-voice emergency services are not available; an audible indicationthat non-voice emergency services are not available; or a mechanicalindication that non-voice emergency services are not available.
 6. Amethod comprising: receiving an indication as to whether non-voiceemergency services are available; analyzing the received indication todetermine if non-voice emergency services are available; and when it isdetermined that non-voice emergency services are available, initiating anon-voice emergency message; and when it is determined that non-voiceemergency services are not available, providing an indication of a lackof non-voice emergency services.
 7. The method of claim 6, wherein theindication of as to whether non-voice emergency services are availableis received via a control channel.
 8. The method of claim 6, furthercomprising: providing an indication that non-voice emergency servicesare available.
 9. The method of claim 6, further comprising: providingat least one of: a visual indication that non-voice emergency servicesare available; an audible indication that non-voice emergency servicesare available; or a mechanical indication that non-voice emergencyservices are available.
 10. The method of claim 6, further comprising:providing at least one of: a visual indication that non-voice emergencyservices are not available; an audible indication that non-voiceemergency services are not available; or a mechanical indication thatnon-voice emergency services are not available.
 11. A computer-readablestorage medium comprising at least one executable instruction that whenexecuted by a processor cause the processor to effectuate operationcomprising: receiving an indication as to whether non-voice emergencyservices are available; analyzing the received indication to determineif non-voice emergency services are available; and when it is determinedthat non-voice emergency services are available, initiating a non-voiceemergency message; and when it is determined that non-voice emergencyservices are not available, providing an indication of a lack ofnon-voice emergency services.
 12. The computer-readable storage mediumof claim 11, wherein the indication is received via a control channel.13. The computer-readable storage medium of claim 11, the operationsfurther comprising: providing an indication that non-voice emergencyservices are available.
 14. The computer-readable storage medium ofclaim 11, the operations further comprising: providing at least one of:a visual indication that non-voice emergency services are available; anaudible indication that non-voice emergency services are available; or amechanical indication that non-voice emergency services are available.15. The computer-readable storage medium of claim 11, the operationsfurther comprising: providing at least one of: a visual indication thatnon-voice emergency services are not available; an audible indicationthat non-voice emergency services are not available; or a mechanicalindication that non-voice emergency services are not available.